home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CD ROM Paradise Collection 4
/
CD ROM Paradise Collection 4 1995 Nov.iso
/
program
/
mgk110a.zip
/
README.DOC
< prev
next >
Wrap
Text File
|
1994-09-20
|
24KB
|
553 lines
MEGIK version 1.1
Multi-Environment Graphical Interface Kit
-------------------------------
Copyright (c) 1994 by Advanced Topics
All Rights Reserved
Welcome to MEGIK! This file contains release notes and general information
about the version 1.1 of the MEGIK development package and about MEGIK/DOS,
the DOS Graphics implementation of the MEGIK API, included in this release.
This file contains the following sections:
1. PRODUCT OVERVIEW
2. PRODUCT RELEASE CONTENTS
3. INSTALLATION
4. THE MEGIK/DOS IMPLEMENTATION
4.1 System Requirements
4.2 Initial Environment Setup
4.3 Setting the MG_OS_DOS constant
4.4 Compiling and Linking
4.5 The MS Graphics Library under 7.0 and above
4.6 Microsoft C/C++ Font Files
4.7 Running the examples
5. REGISTERING THE PACKAGE
5.1 Definition of Shareware
5.2 Ombudsman Statement
5.3 Disclaimer and Agreement
5.4 Registered vs. Unregistered Version
5.5 How to register
6. WHAT'S NEXT
7. GETTING TECHNICAL HELP
1. PRODUCT OVERVIEW
-------------------
MEGIK is a professional-level C development toolkit that lets you create
high-quality application based on a Graphical User Interface (GUI) running
portably on different platforms.
MEGIK makes available to you a powerful API (Application Programming
Interface) through which you build your application and control the GUI using
a simple event-driven approach. This API has been designed to make your
application independent at source code level from the platform on which you
are actually developing the code. The suitable set of MEGIK API libraries
provides then the bridge to the native GUI system, so abstracting you from
the need of coding multiple versions of your application to support multiple
platforms.
The design of the MEGIK API supports a choice of platforms that spans over
plain DOS Graphics, DOS Windows and OS/2 Presentation Manager. Currently,
only libraries for DOS Graphics mode (MEGIK/DOS) are delivered, and you find
them included in this package. The Windows and OS/2 versions are in
preparation and will be released as soon as possible.
Note by the way that using MEGIK/DOS to develop plain DOS GUI applications
is worth the effort by itself, both for the quality of the results you can
achieve if you intend to develop software for MS-DOS and because you obtain
sources that will be portable, with the help of the other MEGIK API libraries
now in preparation, with no modifications on Windows and OS/2.
THIS PACKAGE IS DISTRIBUTED AS A SHAREWARE PRODUCT. This means that you are
free to use it for a trial period, after which you must register to go on in
using it legally. See later in this file for more information about shareware
and registrations, as well as the file REGISTER.DOC included in the package.
2. PRODUCT RELEASE CONTENTS
---------------------------
This release of the MEGIK package comes on two 360K disks (copies on 720K
disks are also available, coming on a single disk that contains all files
of the two-disks distribution package, grouped together). For those who
got MEGIK by BBS, they should have two compressed file whose content
reflects that of the two 360K disks.
Disk 1 contains these files:
__DISK__.01 - Disk 1 identification file
README.DOC - This file
VENDOR.DOC - Information for disk and rack vendors, and BBS operators
BBS.DOC - Information for BBS operators
REGISTER.DOC - Information on how to register the MEGIK package
REGISTER.ITA - Same as above, for Italian users
WHATSNEW.DOC - MEGIK updates history
FILE_ID.DIZ - Standard BBS program description file
MGFILES1.EXE - 1-st MEGIK self-extracting file: see contents below
Disk 2 contains these files:
__DISK__.02 - Disk 2 identification file
FILE_ID.DIZ - Standard BBS program description file
MGFILES2.EXE - 2-nd MEGIK self-extracting file: see contents below
The files MGFILES1.EXE and MGFILES2.EXE are self-extracting archives
containing the binary libraries, include files and documentation, as listed
below (note that these files are organized in a tree of sub-directories).
The section INSTALLATION of this file explains in detail how to de-archive
them to build the installed package. These files have been archived with
LHA version 2.13 Copyright (c) Haruyasu Yoshizaki, 1988-91
Contents of file MGFILES1.EXE:
MGDOS\LIB\MGDBC3M.LIB - MEGIK/DOS Borland C++ 3.x medium model library
MGDOS\LIB\MGDMS6M.LIB - MEGIK/DOS Microsoft C 6.0, C/C++ 7.0 and Visual
C++ 1.x medium model library
MGDOS\LIB\MGDMS6L.LIB - MEGIK/DOS Microsoft C 6.0, C/C++ 7.0 and Visual
C++ 1.x large model library
(included in the REGISTERED version only -*-)
Contents of file MGFILES2.EXE:
DOC\USRGUIDE.DOC - MEGIK User's Guide
DOC\REFMAN.DOC - MEGIK Reference Manual
MGDOS\LIB\EGASYS.FON - Microsoft font file (EGA System Font)
MGDOS\LIB\VGASYS.FON - Microsoft font file (VGA System Font)
MGDOS\INCLUDE\MEGIK.H - MEGIK general include file
MGDOS\INCLUDE\MGDOS.H - MEGIK/DOS platform-specific include file
MGDOS\DOC\PLATDOS.DOC - MEGIK/DOS Platform Manual
MGDOS\EXAMPLES\BMPVIEW:
BMPVIEW.C - Bitmap Viewer source code (sample application)
BMPVIEW.ICO - Bitmap Viewer icon
DOCSMPLE.BMP - How MEGIK doc looks (view with BMPVIEW)
BORLAND.MAK - Bitmap Viewer makefile for Borland
MICROSFT.MAK - Bitmap Viewer makefile for Microsoft
MGDOS\EXAMPLES\CLOCK:
CLOCK.C - Clock source code (sample application)
CLOCK.ICO - Clock icon
BORLAND.MAK - Clock makefile for Borland
MICROSFT.MAK - Clock makefile for Microsoft
MGDOS\EXAMPLES\PCBURGER:
PCBURGER.C - PCburger source code (sample application)
PCBURGER.ICO - PCburger icon
BORLAND.MAK - PCburger makefile for Borland
MICROSFT.MAK - PCburger makefile for Microsoft
MGDOS\LIB\MGDBC3L.LIB - MEGIK/DOS Borland C++ 3.x large model library
(included in the REGISTERED version only -*-)
-*- Unregistered copies of large model libraries are available on request
from Advanced Topics for a nominal fee, covering S&H expenses only
($5 Europe, $10 Others).
3. INSTALLATION
---------------
1) We recommend you should have all the MEGIK stuff installed under a
MEGIK root directory on your development hard disk, say,
C:\MEGIK
Therefore create it if you don't have already one.
2) Transfer on that directory all MEGIK files from the distribution disks
or, if you got MEGIK from a BBS, from the place where you put them after
downloading. Remember in this case to de-archive them if they were found
compressed on the BBS to obtain the same list of files of the distribution
disk (see the PRODUCT RELEASE CONTENTS section above) before proceeding
in the installation.
3) Extract all files from the self-extracting files MGFILESx.EXE. To do
so, simply change you default directory to the MEGIK root directory
C:\> cd \MEGIK
then type the name of the two files
C:\MEGIK> MGFILES1.EXE
C:\MEGIK> MGFILES2.EXE
They will self-extract their contents, creating the suitable
sub-directories and placing their files into them. You can remove
then the two self-extracting files to save space on your disk.
If you have completed successfully these steps, you have obtained an
installation of the MEGIK package containing the general MEGIK documentation
and the MEGIK/DOS libraries, include files and specific documentation to
develop MEGIK application running under DOS Graphics mode.
Refer to the MEGIK/DOS section of this file for instructions about writing,
compiling and running MEGIK/DOS applications (you may want by now simply to
compile and run the sample applications provided with the package).
4. THE MEGIK/DOS IMPLEMENTATION
-------------------------------
This section gives brief notes about MEGIK/DOS, the DOS Graphics mode
implementation of the MEGIK API, which is included in this package.
Detailed information and reference notes are found in the MEGIK/DOS Platform
Manual shipped with the package (for unregistered users, the manual is only
on-disk in the file PLATDOS.DOC under \MEGIK\MGDOS\DOC).
4.1 System Requirements
-----------------------
Developing and running applications using the MEGIK/DOS API requires:
o IBM PC/XT/AT, PS/2 or 100% compatible
o DOS 2.1 or higher
o Hard Disk (recommended)
o EGA or VGA adapter and display
o Microsoft C 6.0, C/C++ 7.0, Visual C++ 1.x or Borland C++ 3.x
4.2 Initial Environment Setup
-----------------------------
You need to setup the environment variables of your compiler to link the
MEGIK environment to your development system. If you have already installed
a C compiler, they are probably already set, so just modify them by adding
the correct MEGIK/DOS directories.
For Microsoft, modify the variable LIB and INCLUDE in your CONFIG.SYS as in
this example (here the compiler is the C 6.0):
set LIB=.;C:\MEGIK\MGDOS\LIB;C:\C600\LIB
set INCLUDE=.;C:\MEGIK\MGDOS\INCLUDE;C:\C600\INCLUDE
After you edited your CONFIG.SYS file, you must REBOOT your computer system
for the new environment variables to take effect.
For Borland C++ 3.x, modify the flag -I and -L in your TURBOC.CFG as in this
example:
-I.;C:\MEGIK\MGDOS\INCLUDE;C:\BORLANDC\INCLUDE
-L.;C:\MEGIK\MGDOS\LIB;C:\BORLANDC\LIB
and in your TLINK.CFG as in this example:
-L.;C:\MEGIK\MGDOS\LIB;C:\BORLANDC\LIB
4.3 Setting the MG_OS_DOS constant
----------------------------------
Declaring to the compiler what platform you are currently running on is a
task demanded to you, by #defining the preprocessor constant MG_OS_xxx
(MG_OS_DOS in the MEGIK/DOS case) somewhere in your code before including
the file MEGIK.H (it uses that constant to decide what platform-specific
additional include file to load).
In order to preserve the portability of the source, we recommend that you
define it outside of the code itself, by using the suitable compiler flag,
i.e.
/DMG_OS_DOS for Microsoft C/C++
-DMG_OS_DOS for Borland C++ 3.x
Of course, you are then free to use this constant in your code to branch
to limited platform-specific portions of code.
4.4 Compiling and Linking
-------------------------
The makefiles supplied with the MEGIK/DOS examples contain complete compiler
flags specifications for building applications using the MEGIK/DOS API. We
recommend creating your application makefile by editing an existing example
makefile.
Here we just recall the naming convention used to identify a MEGIK API
library and the actual names of the shipped MEGIK/DOS API libraries.
A generic MEGIK library file is named
MGxyyyz.LIB
where
x = D | W | O (for Dos, Windows or OS/2 version)
yyy = MS6 | BC3 | ... (for Microsoft C/C++ or Borland C++ 3.x or others)
z = M | L (for Medium or Large memory model)
The libraries supplied with MEGIK\DOS are therefore named:
MGDMS6M.LIB Microsoft C 6.0 and above, medium memory model
MGDMS6L.LIB Microsoft C 6.0 and above, large memory model (reg. only)
MGDBC3M.LIB Borland C++ 3.x medium memory model
MGDBC3L.LIB Borland C++ 3.x large memory model (registered version only)
4.5 The MS Graphics Library under 7.0 and above
-----------------------------------------------
Starting from version 7.0, the Microsoft C/C++ compiler has been released
with a new run-time library file, GRAPHICS.LIB, which contains the code for
the DOS graphics support on top of which the Microsoft version of MEGIK/DOS
was built. The release 6.0 instead included all the graphics stuff in the
standard run-time libraries.
Because of this, if you compile a Microsoft C/C++ 7.0 or Visual C++ 1.x
MEGIK/DOS application you must explicitly link, as opposed to 6.0 programs,
the GRAPHICS.LIB file to your executable.
4.6 Microsoft C/C++ Font Files
------------------------------
The Microsoft C native graphics library (see above) supports fonts by loading
them from disk files when needed.
The MEGIK/DOS library uses two font files for implementing the MEGIK System
Font, VGASYS.FON and EGASYS.FON, which are shipped with the MEGIK/DOS
installation (they are located in the MGDOS\LIB directory). The other fonts
(see the MEGIK/DOS Platform Manual for details) are instead implemented using
the files supplied by the compiler, as in any normal Microsoft C application,
and are therefore not shipped along with the MEGIK package.
4.7 Running the Examples
------------------------
The directory MGDOS\EXAMPLES contains some examples with source code and
makefiles, ready to be compiled and run WITHOUT having to set anything
in your environment (the makefiles use extensively the option flags of the
command-line version of the compilers, so you have just to check the
correctness of the directory names used in the makefile for the compiler and
the MEGIK libraries locations).
To build an example, move to its directory and simply run the makefile
for the correct compiler:
nmake -f microsft.mak for Microsoft C/C++
make -fborland.mak for Borland C++
Then run the application simply starting the executable file generated during
the make process.
WARNING TO MICROSOFT USERS: if you have built an example with the Microsoft
compiler, the resulting application will not run as is and it will stop with
a library error. This is because the installation does not copy automatically
in the examples directories the font files used by MEGIK as System Fonts when
linked to the Microsoft native graphics library, and the initialization
routines of the MEGIK/DOS library complain on this. Therefore copy the file
VGASYS.FON and/or EGASYS.FON from MGDOS\LIB to the directory of the example
you want to run.
See the MEGIK/DOS Platform Manual and the specific paragraph in this file
for more information about dealing with font files in MEGIK/DOS (Microsoft
version) applications.
We recommend you try Bitmap Viewer, a simple viewer of .BMP files. Along with
the source code and the makefiles, you will find the file DOCSMPLE.BMP,
which contains a software preview of one of the pages of the printed MEGIK
User's Guide. Look at it to discover how MEGIK doc looks to registered
users !!
5. REGISTERING THE PACKAGE
--------------------------
5.1 Definition of Shareware
---------------------------
Shareware distribution gives users a chance to try software before buying
it. If you try a Shareware program and continue using it, you are expected to
register. Individual programs differ on details -- some request registration
while others require it, some specify a maximum trial period. With
registration, you get anything from the simple right to continue using the
software to an updated program with printed manual.
Copyright laws apply to both Shareware and commercial software, and the
copyright holder retains all rights, with a few specific exceptions as stated
below. Shareware authors are accomplished programmers, just like commercial
authors, and the programs are of comparable quality. (In both cases, there
are good programs and bad ones!) The main difference is in the method of
distribution. The author specifically grants the right to copy and distribute
the software, either to all and sundry or to a specific group. For example,
some authors require written permission before a commercial disk vendor may
copy their Shareware.
Shareware is a distribution method, not a type of software. You should find
software that suits your needs and pocketbook, whether it's commercial or
Shareware. The Shareware system makes fitting your needs easier, because you
can try before you buy. And because the overhead is low, prices are low also.
Shareware has the ultimate money-back guarantee -- if you don't use the
product, you don't pay for it.
5.2 Ombudsman Statement
-----------------------
ADVANCED TOPICS is a member of the Association of Shareware Professionals
(ASP). ASP wants to make sure that the shareware principle works for you.
If you are unable to resolve a shareware-related problem with an ASP member
by contacting the member directly, ASP may be able to help. The ASP Ombudsman
can help you resolve a dispute or problem with an ASP member, but does not
provide technical support for members' products. Please write to the ASP
Ombudsman at 545 Grover Road, Muskegon, MI 49442-9427 USA, FAX 616-788-2765
or send a CompuServe message via CompuServe Mail to ASP Ombudsman 70007,3536.
5.3 Disclaimer and Agreement
-----------------------------
Users of MEGIK must accept this disclaimer of warranty:
"This software is supplied as is. The author disclaims all warranties,
expressed or implied, including, without limitation, the warranties of
merchantability and of fitness for any purpose. The author assumes no
liability for damages, direct or consequential, which may result from the
use of this software."
The MEGIK package is distributed as shareware, and is provided at no charge
to the user for evaluation. When you the first time get a shareware copy of
the MEGIK package, you are free to use it for up to 30 days, in order to
determine if the software fits your needs. If you decide to continue using it
beyond the 30 day evaluation period, you MUST purchase the registered version
of the MEGIK package.
Commercial users of the MEGIK package must register and pay for their copies
of MEGIK within 30 days of first use or their license is withdrawn.
Site-License arrangements may be made by contacting ADVANCED TOPICS.
5.4 Registered vs. Unregistered Version
---------------------------------------
There are a few differences between the Unregistered Version of the package
(the one freely distributed for evaluation) and the version you will get when
registering your copy. Note that these differences in no way prevent you
from fully evaluating the capabilities of the product.
1) Any application developed with the Unregistered Version of the MEGIK
API libraries shows at start-up a Registration Reminder Screen in a
window that is not closeable for 3 seconds, after that you can close it
by pressing a push button. Thereafter, the application behaves normally
in all respects.
2) The Unregistered Version of the MEGIK package, as well as the Registered
one, includes the COMPLETE documentation on-disk. However, registered
users will get also the printed copies of all the manuals, typed in,
organized and paged-up with a professional word processor, whose feature
of dumping the documents to ASCII files, conserving as much as possible
the original layout, has been exploited to produce the on-disk copies
of the documentation.
This way, the on-disk manuals are not provided to be bound to form the
definitive documentation (they lack figures, indexes, page headers and
footers, page numbering) but anyway they are still printable, look clear
and serve well to understand MEGIK and produce your trial applications.
REMEMBER: possible discrepancies in the layout of the documentation files
are due only to the (commercial) software used to obtain the
ASCII disk files from the original copies (masters for the
printed manuals). Of course, the printed manuals does not show
these effects.
Summarizing, the Registered Version of the MEGIK package gives you additional
features and benefits, as listed below:
o The license to LEGALLY develop software with MEGIK beyond the trial
period, with no run-time royalties. Unregistered users can only use
the MEGIK package for up to 30 days. Continued use of the unregistered
package after the 30 day trial period is a violation of the copyright
law.
o The printed User's Guide, Reference Manual and MEGIK/DOS Platform
Manual, a total of over 300 pages of high-quality, comprehensive
and professionally presented documentation, with indexes and
illustrations.
o One year of free Technical Support, via Fax, E-Mail or mail.
o Applications developed with the registered version of the MEGIK API does
not show the Registration Reminder Screen upon application start-up.
o The package delivered upon registration is always updated to the latest
release available.
o Substantial discounts on upgrades and new versions. The registered
user will be promptly informed about any available new release.
5.5 How to register
---------------------
At present we accept payments by credit cards, checks, international postal
money orders and currency. For detailed instructions about terms and
conditions of registration and a registration form ready to be printed, see
the file REGISTER.DOC included with the package (REGISTER.ITA for Italian
users).
6. WHAT'S NEXT
--------------
The two further implementations of the MEGIK API planned by now, MEGIK/WIN
for Windows 3.1 and MEGIK/OS2 for OS/2 2.1, are in preparation and will be
released as soon as possible.
Moreover, we are already working to make the MEGIK package still more
interesting. This includes the enrichement of the API with features such as
multi-line text edit fields, clipboard management, help system facilities
and more, and the release of supporting tools as a Window Designer and a
Cross-platform Resource File Compiler to integrate resources in the MEGIK
Development System.
Remember: registering now helps us working harder and releasing faster !!!
7. GETTING TECHNICAL HELP
-------------------------
To better consider our registered users' help requests, and also to keep
the cost of the product registration down, at the moment we cannot provide
telephone technical support. Instead you may contact us, and you will be
replied also, by Fax, Internet E-Mail or Air-Mail.
Unregistered users will only receive basic technical support in a limited
extent.
We recommend to provide, with your request of help, as much as possible of
the following information:
- MEGIK API implementation and version
- Computer make and model
- Amount of memory (RAM)
- Version of DOS
- Graphics card
- Monitor
- Brand and Version of mouse driver
- Error messages (if any) yielded by MEGIK or other
- Contents of your CONFIG.SYS file
- Contents of your AUTOEXEC.BAT file
- Compiler used and related settings
Please have your product serial number included in communications, too.
All questions must be submitted to
ADVANCED TOPICS
v. XXV Aprile 9/B
10045 Piossasco (TO) - ITALY
Fax: 39-11-323607
E-Mail: mc3758@mclink.it
_______
____|__ | (R)
--| | |-------------------
| ____|__ | Association of
| | |_| Shareware
|__| o | Professionals
-----| | |---------------------
|___|___| MEMBER